The product owners required that the goals would not be included amongst the rest of the requirements and instead the goal requirements have this chapter where each goal is given an unique ID. Considering that Lausen stated that goal requirements should be outside the scope of the developers \cite{lauren4} this arrangement is even preferred. The goals were elicitated during documentation studies, group interview and brainstorming. They were specified by feature requirements. They are not prioritized or not further traced as they are not a part of comparable with the other requirements. 
\\\\
The main goals and purpose of the finished Get to the point will be:

\begin{description}
 \item[G1. Profit] \hfill \\ The applications features should be thought through from a competition perspective.
 \item[G2. Finding stores] \hfill \\ Users with a smartphone should be able to locate stores through the use of this product.
 \item[G3. OS support] \hfill \\ The application should give Android OS and iOS support of versions that has been released prior to 6th of december 2011. 
\end{description}